
<!DOCTYPE html>
<html class="client-nojs" lang="en" dir="ltr">
<head>
<meta charset="UTF-8"/>
<title>Hugin Parameters for Control Point Detectors dialog - PanoTools.org Wiki</title>




<style media="screen" type="text/css" title="Screen style sheet"> @import url(manual.css); </style>

<meta name="generator" content="MediaWiki 1.35.3"/>
<meta name="viewport" content="width=device-width, initial-scale=1"/>





<!--[if lt IE 9]><![endif]-->
</head>
<body class="mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Hugin_Parameters_for_Control_Point_Detectors_dialog rootpage-Hugin_Parameters_for_Control_Point_Detectors_dialog skin-vector action-view skin-vector-legacy">


<div id="content" class="mw-body" role="main">
	<a id="top"></a>
	
	
	<h1 id="firstHeading" class="firstHeading" lang="en">Hugin Parameters for Control Point Detectors dialog</h1>
	<div id="bodyContent" class="mw-body-content">
		<div id="siteSub" class="noprint">From PanoTools.org Wiki</div>
		
		
		
		
		
		
		<div id="mw-content-text" lang="en" dir="ltr" class="mw-content-ltr"><div class="mw-parser-output"><p>This dialog is accessible from the <a href="Hugin_Preferences.html#Control_Point_Detectors" title="Hugin Preferences">Control Point Detectors tab</a> of the <a href="Hugin_Preferences.html" title="Hugin Preferences">Hugin Preferences</a> and is used to change the parameters of the control point detectors.
</p><p>This page gives a description of all options. <a href="Control_Point_Detector_Parameters.html" title="Control Point Detector Parameters">Control point detector parameters site</a> gives an overview about the settings for the different control point detectors and for different use cases.
</p>
<div id="toc" class="toc" role="navigation" aria-labelledby="mw-toc-heading"><input type="checkbox" role="button" id="toctogglecheckbox" class="toctogglecheckbox" style="display:none" />
<ul>



</ul>
</div>

<h1><a name="Description"><span class="mw-headline">Description</span></a></h1>
<p>You should give your parameter-set a meaningful name, because this name is shown in the GUI on the <a href="Hugin_Photos_tab.html" title="Hugin Photos tab">Photos tab</a>.
</p>
<h1><a name="Type"><span class="mw-headline">Type</span></a></h1>
<h2><a name="All_images_at_once"><span class="mw-headline">All images at once</span></a></h2>
<p>With this setting all images are transferred at once to the control point detector. This was the default setting of <a href="Hugin.html" title="Hugin">Hugin</a> versions before 2010.2. 
</p>
<h2><span id="Autopano_(by_A._Jenny)"></span><a name="Autopano_.28by_A._Jenny.29"><span class="mw-headline">Autopano (by A. Jenny)</span></a></h2>
<p>This is the same procedure as <b>All images at once</b> with some modifications for using <a href="Autopano.html" title="Autopano">autopano</a> by Alexandre Jenny (only Windows and Linux, there is no MacOS version).
</p>
<h2><a name="Panorama_with_stacks"><span class="mw-headline">Panorama with stacks</span></a></h2>
<p>This setting is intended for panoramas with stacks. In the first step it selects the image with the median exposure of every stack. Then it tries to match these median exposed images. After this step all image stacks should be connected.
</p><p>Then it tries to connect the images of every stack by using the program given under <b>Detector for stacks</b>.
</p><p>When your panorama does not contain stacks, it's does the same as <b>All images at once</b>.
</p>
<h2><a name="Multi-row_panorama"><span class="mw-headline">Multi-row panorama</span></a></h2>
<p>As the name implies this setting is for multi-row panoramas. But it works also for single row panoramas.
It uses a heuristic approach to speed up and optimize the detector step.
</p><p>The following steps are executed:
</p><p>1.) Try to connect all consecutive images. The result will be a project with one or more groups of connected images. With luck each of these groups will correspond with a row of the panorama.
</p><p>2.) Then take the first and last images from each group and match them all together in one go.  With luck there will be a single group of connected images in the project.
</p><p>If you selected <b>Try to connect all overlapping images</b> on the Advanced tab, it tries to connect all overlapping images. This happens only if the steps above were successful. Only then the following steps are executed:
</p><p>3.) Optimize panorama (it optimizes only yaw and pitch) to get a rough position of all images.
</p><p>4.) Now try to link all overlapping images which are not yet connected.
</p>
<h2><a name="Multi-row_panorama_with_stacks"><span class="mw-headline">Multi-row panorama with stacks</span></a></h2>
<p>This setting combines <b>Panorama with stacks</b> and <b>Multi-row panorama</b>. It works like <b>Panorama with stacks</b>, but for connecting the median exposed images it uses the algorithm described under <b>Multi-row panorama</b>.
</p>
<h2><a name="Prealigned_panorama"><span class="mw-headline">Prealigned panorama</span></a></h2>
<p>This setting works only if the rough positions of the images are defined in the project. It tries to link all overlapping images.
</p><p>If the advanced option <b>Work only on image pairs without control points</b> is selected (default), it skips all image pairs which are already connected by <a href="Control_points.html" title="Control points">Control points</a>. Otherwise it creates also control points for already connected images.
</p>
<h1><a name="Programs"><span class="mw-headline">Programs</span></a></h1>
<p>On the notebook you can give the paths and parameters for the individual programs.
</p>
<h2><a name="Detector"><span class="mw-headline">Detector</span></a></h2>
<p>Here you can give the program name (inclusive path) and the parameters for the control point detector. 
You can use a one-step setup. In this you invoke the control point detector with a list of image files and it returns a project file with the found control points. If you use <a href="Cpfind.html" title="Cpfind">cpfind</a> with the --cache parameter you can specify a cleanup argument to delete the generated keypoints file at the end of the detection run.
</p><p>A further speed up of the detection phase (especially for the multi-row panorama settings) can be achieved by using the two-step detectors approach. Currently only <a href="Autopano-sift-C.html" title="Autopano-sift-C">autopano-sift-C</a> and <a href="Cpfind.html" title="Cpfind">cpfind</a> support this approach. In this case you have two separate programs: a feature descriptor and a feature matcher. The feature descriptor extracts the features from the images and stores a keyfile in the temp directory. Then the feature matcher reads these keyfiles and tries to match overlapping images. At the end of the detection phase the temporary keyfiles are deleted.
You have to give the program name and arguments for both programs. A big speed up can be achieved for the multi-row and prealigned settings.
</p>
<h2><a name="Detector_for_stacks"><span class="mw-headline">Detector for stacks</span></a></h2>
<p>Here you can define the control points detector which works on stacks (in setting <b>Panorama with stacks</b> and <b>Multi-row panorama with stacks</b> only). You can use e. g. <a href="Align_image_stack.html" title="Align image stack">Align image stack</a> for aligning the stack. 
If you used a tripod, you can leave this field empty. Then the detector does not run on the stacks. In this case you can use linking of the image positions on the Hugin Images tab<a class="external" href="https://wiki.panotools.org/Hugin_Images_tab">[*]</a>.
</p>
<h2><a name="Hints"><span class="mw-headline">Hints</span></a></h2>
<p>Typical tweaks might be to:
</p>
<ul><li>Set <i>--noransac</i> for <a href="Autopano-sift.html" title="Autopano-sift">autopano-sift</a> when using non-<a href="Rectilinear_Projection.html" title="Rectilinear Projection">rectilinear Projection</a> input images.</li>
<li>Set <i>--size</i> for <a href="Autopano-sift.html" title="Autopano-sift">autopano-sift</a> which by default downsizes images to 700 pixels before matching.</li>
<li>Some operating systems have problems supplying more than 120 or so photos at one time to these external tools, with autopano-sift-C 2.5.1 or later you can use these alternative arguments to specify input via a project file: <i>--maxmatches %p %o %s</i></li>
<li>MacOS only: If you are using control point detector which are contained in the bundle, give only the program name (without path). Hugin tries to find the program then inside the bundle.</li></ul>

<!--
Transclusion expansion time report (%,ms,calls,template)
100.00%    0.000      1 -total
-->


</div></div><div class="printfooter">Retrieved from "<a dir="ltr" href="https://wiki.panotools.org/index.php?title=Hugin_Parameters_for_Control_Point_Detectors_dialog&amp;oldid=14918">https://wiki.panotools.org/index.php?title=Hugin_Parameters_for_Control_Point_Detectors_dialog&amp;oldid=14918</a>"</div>
		</div></div></body></html>